Search Results

The SAE Aerospace Information Report AIR5315 – Generic Open Architecture (GOA) defines “a framework to identify interface classes for applying open systems to the design of a specific hardware/software system.” [sae] JAUS Service (Interface) Definition Language defines an XML schema for the interface definition of services at the Class 4L, or Application Layer, and Class 3L, or System Services Layer, of the Generic Open Architecture stack (See Figure 1 below). The specification of JAUS services shall be defined according to the JAUS Service (Interface) Definition Language document.

The SAE Aerospace Information Report AIR5315 – Generic Open Architecture (GOA) defines “a framework to identify interface classes for applying open systems to the design of a specific hardware/software system.” [sae]JAUS Service (Interface) Definition Language defines an XML schema for the interface definition of services at the Class 4L, or Application Layer, and Class 3L, or System Services Layer, of the Generic Open Architecture stack (See Figure 1 below). The specification of JAUS services shall be defined according to the JAUS Service (Interface) Definition Language document.

This SAE Aerospace Information Report (AIR) discusses characteristics of data communications for the Joint Architecture for Unmanned Systems (JAUS). This document provides guidance on the aspects of transport media, unmanned systems and the characteristics of JAUS itself that are relevant to the definition of a JAUS transport specification.

This SAE Aerospace Information Report (AIR) discusses characteristics of data communications for the Joint Architecture for Unmanned Systems (JAUS). This document provides guidance on the aspects of transport media, unmanned systems and the characteristics of JAUS itself that are relevant to the definition of a JAUS transport specification.

This SAE Aerospace Standard (AS) defines a data communications Transport Layer for the Joint Architecture for Unmanned Systems (JAUS). This Transport Specification defines the formats and protocols employed for the transport of JAUS messages between compliant entities for all supported link-layer protocols and media.

This document defines a set of standard application layer interfaces called JAUS Unmanned Ground Vehicle Services. JAUS Services provide the means for software entities in an unmanned system or system of unmanned systems to communicate and coordinate their activities. The Unmanned Ground Vehicle Services represent the platform-specific capabilities commonly found in UGVs, and augment the Mobilty Service Set [AS6009] which is platform-agnostic. At present ten (10) services are defined in this document. These services are categorized as:

This SAE Aerospace Standard (AS) defines a set of standard application layer interfaces called JAUS UMV Services. JAUS Services provide the means for software entities in an unmanned system or system of unmanned systems to communicate and coordinate their activities. The UMV Services represent the platform-specific capabilities commonly found in UMVs and augment the Mobility Service Set (refer to AS6009) which is platform-agnostic. At present, 12 services are defined in this document. While these services are presented alphabetically within this document, they also can be logically categorized as: Platform Description Services: This service provides information about the vehicle platform, including mobility limits and geometric properties: ○ Platform Specification Service. Propulsion and Driver Services: These services provide the control and monitoring capabilities to the vehicle’s propulsion system(s).

This SAE Aerospace Standard (AS) specifies a data communications layer for the transport of messages defined by the Joint Architecture for Unmanned Systems (JAUS) or other Software Defined Protocols (SDP). This Transport Specification defines the formats and protocols used for communication between compliant entities for all supported link-layer protocols and media. Although JAUS is the SDP used as the example implemented throughout this document, AS5669 can be used for any SDP that meets the required capabilities. A Software Defined Protocol is defined as an application data interface for communicating between software elements. The SDP is agnostic of the underlying communications protocol and in fact communicates in much the same manner regardless if the communicating entities are collocated in the same memory space or separated by a satellite link.

This SAE Aerospace Recommended Practice (ARP) describes terminology specific to unmanned systems (UMSs) and definitions for those terms. It focuses only on terms used exclusively for the development, testing, and other activities regarding UMSs. It further focuses on the autonomy and performance measures aspects of UMSs and is based on the participants’ earlier work, the Autonomy Levels for Unmanned Systems (ALFUS) Framework, published as NIST Special Publication 1011-I-2.0 and NIST Special Publication 1011-II-1.0. This Practice also reflects the collaboration results with AIR5665. Terms that are used in the community but can be understood with common dictionary definitions are not included in this document. Further efforts to expand the scope of the terminology are being planned.